Category: Geeks r Us
Hi all. At work we are using jaws7.0. Here is the issue we are having. We have jaws set to startup when windows starts because we have a log on screen so we can get into our profile. However sometimes jaws will load without our knowledge. We don't know it's loaded until we do the control-alt-delete to log on and find jaws is speaking. We'd like it to say jaws for windows is ready like it's suppose to. Anyone else having this issue with jaws7 at windows startup? Thanks. Just for the record it's win2000
Troy
hmmm, i've never heard of that problem myself. maybe someone else can help
perhaps the computer is slowing down and the sound driver hasn't kicked in yet?
Perhaps JAWS for Windows is not ready? If you ever hear that message, run for your life!
That's interesting, I wonder if there is such a message "jaws is not ready" <grin>.
Actually, I think Frequency may be on to something here. Could it be that jaws is loading into the registry too early? There is a way to control when jaws (or any program loads), but I don't know how to do it. Maybe your tech gurus at work know of a way.
Bob
I've had that problem since I've upgraded from windows ME to xp home; only when I tell Jaws to start automaticly it doesn't speak at all. It comes up like it's supposed to, because I've had sighted people tell me that, but if I want it to talk, I have to unload, then reload it to get it to work properly.
hmmm, i use xp myself, and have never heard of this problem.
Good evening. Juliet's post brings to mind a solution I used on one client's machine although this doesn't help those who need to log on to networks. Sometimes in WinXP if Jaws is set to run first it doesn't always hook in correctly. This leads to problems of the start menu not reading and other types of dificulties. If Jaws is set to run after startup or put in to the startup group this problem disapears because windows boots first and then Jaws hooks in properly.